Create Backup Set

From v7.11.0.0 onwards, %edition_name% supports 2 backup modes when creating a backup set for MS SQL Server, VSS mode and ODBC mode.

Backup Requirements

Please ensure that the following requirements are met:


Considerations for backup and restore of system databases

Refer to the following tables for considerations for backup and restore of system databases:

Considerations for backup of system databases:

SQL server maintains a set of system level database which are essential for the operation of the server instance.

Several of the system databases must be backed up after every significant update, they includes:

This table summarizes all of the system databases.

System databaseDescriptionBackup requiredSuggestion
master

The database that records all of the system level information of a SQL server system.

Yes

To back up any database, the instance of SQL server must be running.

Startup of an instance of SQL server requires the master database is accessible and at least party usable.

Back up the master database as often as necessary to protect the data sufficiently for your business needs.

Microsoft recommends a regular backup schedule, which you can supplement with manual backup after any substantial update.

model

The template for all databases that are created on the instance of SQL server.

Yes

Backup the model database only when necessary, for example, after customizing its database options.

Microsoft recommends that you create only full database backups of model, as required. Because model is small and rarely changes, backing up the log is unnecessary.

msdb

The msdb database is used by SQL Server Agent for scheduling alerts and jobs, and for recording operators.

It also contains history tables (e.g. backup / restore history table).

Yes

Back up msdb whenever it is updated.

tempdb

A workspace for holding temporary or intermediate result sets.

This database is recreated every time an instance of SQL server is started.

No

The tempdb system database cannot be backed up.

distribution

The distribution database exists only if the server is configured as a replication distributor.

It stores metadata and history data for all types of replication, and transactions for transactional replication.

Yes

Replicated databases and their associated system databases should be backed up regularly.


Considerations for restore of system databases:
System databaseRestore suggestion
master

To restore any database, the instance of SQL server must be running. Startup of an instance of SQL server requires that the master database is accessible and at least party useable.

Restore or rebuild the master database completely if master becomes unusable.

modelRestore the model database if:
  • The master database has been rebuilt.
  • The model database has been damaged, for example due to media failure.
  • The model database has been modified, in this case, it is necessary to restore model from a backup when you rebuild master, because the Rebuild Master utility deletes and recreates model.
msdbRestore the msdb database if the master database has been rebuilt.
distribution

For restore strategies of distribution database, please refer to the following online document from Microsoft for more details:

http://msdn.microsoft.com/en-us/library/ms152560.aspx

Limitation

  1. %edition_name% does not support backup of MS SQL server in cluster environment, only standalone environment is supported.
  2. For VSS backup mode:
  3. You cannot create database snapshots on FAT32 file system or RAW partitions. The sparse files used by database snapshots are provided by the NTFS file system.
  4. SQL Server Version:
  5. Restore to other SQL server:

Best Practice and Recommendation

  1. For VSS backup mode, it is suggested to set the backup schedule to a time when system activity is low to achieve the best possible performance.
  2. It is recommended to use ODBC backup mode for backup of database with a high volume of transaction, since such setup may require frequent backups. Transaction log backup (which is only supported by ODBC backup mode) can be performed periodically, and is less resource intensive than VSS based backup.
  3. For maximum data protection and restore options, it is recommended to configure:
        At least one offsite or cloud destination
        At least one local destination for fast recovery
  4. Perform test restores periodically to ensure your backup is set up and performed properly. Performing recovery test can also help identify potential issues or gaps in your recovery plan. It's important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test and it is important to identify those flaws.
  5. The Restore Raw File option is for advanced MS SQL Server administrator and should only be used if you have in-depth knowledge and understanding of your MS SQL Server, otherwise, it is not recommended to use this option as there are additional MS SQL techniques required to perform the manual restore.

Set the name of the backup set

Key:

Field Description
Name This is the name of the backup set. You can create a meaningful name for it.
Backup set type Enter the correct backup type from the drop down box.
Backup mode Select the backup mode from the drop down box.
Server Select to backup multiple SQL instances or a specific instance from the drop down box.
Login ID The login ID to access your MS SQL server. Default is sa.
Password The login password to your MS SQL server.

To create a backup set name:

  1. Type in a meaningful backup set name.
  2. Enter correct backup set type, eg: MS SQL Server Backup.
  3. Select the backup mode from the drop down box, eg: VSS (without staging data; support full, differential and incremental backup), ODBC (with staging data; support full, differential and transaction log backup).
  4. Select to back up multiple SQL instances or a specific instance from the drop down list.
  5. Change the Login ID if necessary, by default 'sa'.
  6. Enter correct password.
  7. Click [Next] button to continue.
  8. Note: Click [Next] button will start the verifying process.